"XPNET 3.1 Interim Bug Fixes (IBFs) and Enhancements - APPC"

SCR #    Change Description
-----    ------------------

SCR #3389     LU62       - rel3^ver0^lu6208^070404
04-APR-07                  rel3^ver1^lu6203^20070404

           Reference:  Case #432823

           Symptom: XPNET trap number 11 while processing an error
              in the LU62 protocol (procedure LU62^ERROR^HANDLER^TASK
              is on the stack).

           Problem: When certain types of errors occur, variables on
              the stack could be corrupted by a move of incorrect
              length.  This problem existed in XPNET 3.0, but did not
              surface until XPNET 3.1 because the PTAL compiler used
              for that release reversed the order of variables on the
              stack.  The variables which were corrupted in 3.0 did
              not matter at this point in the code, the variables
              corrupted for 3.1 do matter causing the trap.

           Change: Changed the length of a move in procedure
              LU62^ERROR^HANDLER^TASK of the LU62 protocol so it
              no longer corrupts variables on the stack.

          Implementation:  Install the new LU62 file on XPNET subvol.
             Rebuild the NETWORK object using the NETB file.

             If XPNET 3.0 and on RISC machine, accelerate the NETWORK
             object as shown in the XPNET.NETAXCL file.

           Dependencies: None.


SCR #3615     LU62       - rel3^ver1^lu6204^20131115
15-Nov-13     LU62       - rel3^ver2^lu6201^20140228

          Reference:  Case #01495256

          Symptom:
             1) SNAX/APC not doing ASCII to EBCDIC translation
             2) Allocate can occasionally fail with an Invalid_Indicator
                error

          Problem:
             1) XPNET LU 6.2 doesn't support the Mapped API and that
                prevents SNAX/APC doing ASCII to EBCDIC translation
             2) LU 6.2 module allows Allocate's Sync Level to default

          Change:
             1) Added support for Mapped API to XPNET LU 6.2.
                In addition to setting the partner^tp^type in the
                [mc^]allocate verb, MAPPED ON will now activate the
                mapped API verbs. Only the subset of mapped verbs that
                are needed by XPNET are supported.

             2) Made sure that Allocate's Sync Level is always set
                correctly

          Implementation:  Replace existing files with the files
             associated with this fix (LU62).  Re-build the network
             object file using the NETB and NETBC files.
             Stop and re-start all nodes affected.

           Dependencies: Not in 3.0